copilot-bluespec: Include in mainline copilot repo. Refs #623. - #625

Change Manager: The README under copilot-bluespec and the cabal file are not the same. I can understand the difference in the Cabal file but not the one in the the README.

Can we have one commit that just adds copilot-bluespec exactly as it is in https://github.com/Copilot-Language/copilot-bluespec/ but in a sub-directory, with zero changes, and then in another commit make the change to the CHANGELOG adjusting the issue numbers, third commit adding the new entry to the CHANGELOG for #623, and nothing else?

I prefer to leave the change to the cabal file and the README for a separate issue. Let's try to keep this as simple as possible. There has to be a commit in the history of copilot such that, when that commit is checked out, diff <copilot-repo/copilot-bluespec> <copilot-bluespec-repo#currentmaster> only shows differences in .git/.github (no differences in any other file).

I have reverted the changes to the README and .cabal file for now. I have also split out the part that updates the issue numbers in the changelog into a separate commit.

Implementor: Fix implemented, review requested.

Change Manager: The commit message of the first (oldest) commit states that:

"It also adjusts the copilot-bluespec changelog to make the old issues refer to copilot-bluespec#<ISSUE_NUM> so that they are not interpreted as related to the main repo."

but I think that's done by the second commit now.

Implementor: Fix implemented, review requested.

Change Manager: The middle commit refers to the wrong issue number in the commit message (it refers to the PR number, not the issue number). The summary line reads:

copilot-bluespec: Adjust issue numbers in changelog. Refs #625.

when it should read:

copilot-bluespec: Adjust issue numbers in changelog. Refs #623.

Implementor: Fix implemented, review requested.

Change Manager: Verified that:

• Solution is implemented:
  • The code proposed compiles and passes all tests. Details:
    Build log: https://app.travis-ci.com/github/Copilot-Language/copilot/builds/275533476
  • The solution proposed produces the expected result. Details:
    The following dockerfile checks out the latest version of copilot-bluespec, v4.4, and compares it against the version being merged, ignoring changes in expected files, namely those related to Git, Github or the CHANGELOG, checking that there are no other differences, after which it prints the message "Success":

    FROM ubuntu:noble
    
    ENV DEBIAN_FRONTEND=noninteractive
    RUN apt-get update
    
    RUN apt-get install --yes git
    RUN git config --global advice.detachedHead false
    
    CMD git clone $REPO $NAME \
        && cd $NAME \
        && git checkout $COMMIT \
        && cd .. \
        && git clone -b v4.4 https://github.com/Copilot-Language/copilot-bluespec copilot-bluespec-original \
        && diff --exclude '.git' --exclude '.github' --exclude '.gitignore' --exclude 'CHANGELOG' -r $NAME/copilot-bluespec copilot-bluespec-original \
        && echo "Success"

    Command (substitute variables based on new path after merge):

    $ docker run -e REPO=https://github.com/GaloisInc/copilot-1 -e NAME=copilot -e COMMIT=7433ba32d87727f947357f78293bd8b900bba0f6 copilot-verify-623
    

• Implementation is documented. Details:
  CHANGELOG updated to make old issues point to original repo. No other changes needed.
• Change history is clear.
• Commit messages are clear.
• Changelogs are updated.
• Examples are updated. Details:
  No updates needed.
• Required version bumps are evaluated. Details:
  Bump not needed; change imports existing package without affecting API.